Method and system of providing network addresses to in-premise devices in a utility network

ABSTRACT

One example embodiment provides a method and system where a node in a utility network receives a block of IPv6 network addresses from an access point in the utility network. The utility node allocates an IP network address from the block of IPv6 network addresses received from the access point to an in-premise device which communicates to the utility node over an in-premise network which is not IP based. The utility node proxies the allocated IP address to the utility network, allowing other nodes on the utility network to address and communicate with the in-premise device.

RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication Ser. No. 60/899,328 entitled “SYSTEM & METHOD OFCOMMUNICATIONS FOR UTILITY & HOME NETWORK SERVICES USING IPV6 AND IPPROTOCOL SUITE” filed Feb. 2, 2007.

BACKGROUND

1. Field of the Invention

The field of the invention relates generally to systems for controllingand delivering commodities, and more particular to IP-based packetcommunication systems for monitoring, controlling, and deliveringcommodities.

2. Related Background

Automated Meter Reading (AMR) systems and Automated Meter InfrastructureSystems (AMI) provide services and capabilities to monitor and/or reportthe usage (or consumption) of a commodity, such as water, electricity,gas, etc. Such systems provide communication between a commodity meterand one or more systems to report, bill, etc. Commodity meteringinformation, as well as other information, is typically reported fromthe network devices associated with the meters to the reporting andbilling systems.

The present invention seeks to overcome the limitations of conventionalutility networks.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a generalized block diagram of a computer-based system thatmay be used to implement the present invention, according to oneembodiment of the invention.

FIG. 2 is a generalized block diagram of a computer-based system thatmay be used to implement the present invention, according to oneembodiment of the invention.

FIG. 3 is a generalized flow diagram illustrating a process forproviding network addresses for nodes in a local area network, accordingto one possible embodiment.

FIG. 4 is a generalized communications flow diagram of illustratingregistering a nodal device with an access point, according to oneembodiment of the invention.

FIG. 5 is a generalized block diagram illustrating registering arechargeable hybrid car with an access point, according to oneembodiment of the invention.

FIG. 6 is a generalized block diagram of a node as may be found incommunications network, according to one embodiment of the invention.

FIG. 7 is a generalized block diagram of an access point as may be foundin a communications network, according to one embodiment of theinvention.

FIG. 8 is a generalized block diagram of back office system as may befound in a communications network, according to one embodiment of theinvention.

FIG. 9 is a generalized block diagram illustrating a sub-network of autility node, according to one possible embodiment.

FIG. 10 is a generalized block diagram illustrating a network where andIPv4 tunnel connects an IPv6 LAN to and IPv6 back office system,according to one embodiment of the invention.

FIG. 11 is a generalized block diagram illustrating packet flow betweenthe access point associated with the IPv6 LAN and the BOS through theIPv4 WAN, according to one embodiment of the invention.

FIG. 12 is a generalized block diagram illustrating a network where IPv6packets are passed through an IPv4 WAN, according to one possibleembodiment.

FIG. 13 is a generalized block diagram illustrating a network where IPv4packets are passed through an IPv6 LAN, according to one possibleembodiment.

SUMMARY

The present invention provides a system and method for IP-basedcommunication where utility nodes in an IPv6 utility network are able toallocate IPv6 addresses to in-premise devices which communicate with theutility node over a non-IP based in-premise communications network.Access points allocate blocks of IPv6 addresses to utility nodes forallocation to the in-premise devices. The allocated blocks may becontinuous, and may be unique to the given utility node. The utilitynode may proxy addresses allocated to in-premise devices to other nodes,including access points, allowing other nodes in the utility network toaddress the in-premise device despite the in-premise device not being onan IP network.

DETAILED DESCRIPTION

The present invention is described in the context of a specificembodiment. This is done to facilitate the understanding of the featuresand principles of the present invention and the present invention is notlimited to this embodiment. In particular, the present invention isdescribed in the context of a system for remotely reading, controllingand managing electronic devices in a utility network. The presentinvention is applicable to other systems for network-based management ofelectronic devices and commodity meters.

The example embodiment provides for a network-based system and method ofmonitoring and controlling a utility meter in a utility network.

FIG. 1 is a generalized block diagram of a utility network 100 that maybe used to implement embodiments of the present invention. Utilitynetwork 100 may include one or more electronic devices 101. In apreferred embodiment, the electronic devices 101 may be connected over awireless local area network (LAN) 102. In the example of a utilitynetwork, the LAN may be a neighborhood area network (NAN) correspondingto a neighborhood or service area for the utility. As shown in theexample embodiment, multiple LANs may be used, which may or may notoverlap, such that a given electronic device can be connected to (or bepart of) only one wireless LAN or multiple wireless LANs. The electronicdevices may be any type of electronic device. Examples of electronicdevices include utility nodes, which may include a utility meter or mayconnect to a utility meter. A utility meter is a device which is capableof measuring a metered quantity, typically a commodity like electricity,water, natural gas, etc. Utility nodes which connect to a utility metermay include a network interface card (NIC) for communicating on anetwork, and may include one or more RF transceivers for communicatingon one or more wireless LANs. Other examples of electronic devicesinclude communication devices, such as set top boxes (as may be used incable television or satellite television delivery), household appliances(e.g. refrigerator, heater, light(s), cooking appliances, etc.),computers or computing devices (e.g. game consoles, storage devices,PCs, servers, etc.) networking devices such as relay, gateway, accesspoint, router, or other networking devices, phones or cell phones,battery storage device, transportation devices, transportation vehicles(for example: an electric or hybrid car or other vehicle), entertainmentdevices (e.g. TVs, DVD players, set top boxes, gaming consoles, etc.),or other devise which may be found in a home, business, roadway orparking lot, or other location. Relays may handle communication betweenelectronic devices 101 and the wireless LAN 102. For example, a relaycould provide communication between the electronic device and theinfrastructure of the wireless network. Unless otherwise noted, otherdevices in the network such as meters, electronic devices, gateways,etc. may also perform as relays, and relays may perform the functions ofother devices or software on the network.

The wireless LAN 102 may be any type of wireless network, and may useany frequency, communications channel or communications protocol.

The LANs 102 are typically connected to one or more access points (AP)103. A given LAN may be connected to only a single AP, or may beconnected to two or more access points. The access points 103 may beconnected to one or more wide area networks (WAN) 104. The WANs 104 maybe connected to one or more back office systems (BOS) 105. The backoffice system may handle a variety of business or management tasks,including participation in the collection of metering information,managing metering devices, security for the network, or other functionsas may be desired in an AMI network. Examples of back office systemsinclude billing and accounting systems, proxy servers, outage detectionsystems (as may be used in a utility network), data storage systems,etc.

Nodes within the communications network, which may be a LAN or a WAN, ora combination of both, may communicate using one or more protocols.Nodes may include an electronic device, a relay, an access point, arouter, or a BOS. Some nodes may be able to communicate using IPv6, somemay be capable of communicating on IPv4, while some may be capable ofcommunicating on either IPv4 or IPv6. Some nodes may be capable ofencapsulating IPv6 packets in an IPv4 packet. Additionally, some nodesmay be able to establish an IPv4 tunnel through an IPv6 network. Thecommunication between nodes is described more fully below.

Assigning and Registering Network Addresses in Communication Networks

FIG. 2 is a generalized block diagram of a communications networkincluding a LAN 200 and LAN 206. The LANs connect nodes 202 and accesspoints 201. As shown, LAN 200 has two access points, and LAN 206 hasonce access point. A domain name server (DNS) 203 is connected to LAN200 and LAN 206 through access point 201 to a communications network204. In the presently preferred embodiment, DNS server 203 is capable ofreceiving and processing dynamic updates, thus providing a dynamic DNSservice. Dynamic updating of DNS is in accordance with IETF RFC 2136.Communications network 204 may be any type of communications networkincluding, without limitation, a LAN, WAN, wireless, fixed line, privatenetwork, virtual private network, etc. In the presently preferredembodiment the communications network 204 is a wide area network, andmay use one or more communications protocols such as IPv4 or IPv6. Oneor more computing devices 205 connect to the communications network 204.A message to a node 202 from the computing device 205 may be sent usinga network address for the node. Computing device 205 may be any device,combination of devices, network management system, server, back officesystems (BOS), computers, network devices, communications devices,software application or component which is capable of communicating withan access point or node via the communication network 204. A second LAN206 may also be connected to the DNS server 203 and the communicationsnetwork 204. A DNS server may be dedicated to a single LAN, or two ormore LANs may share a DNS server. As shown, LAN 200 and LAN 206 do notoverlap, in that none of the nodes, and none of access points shown aremembers of both LAN 200 and LAN 206. Alternate embodiments may have oneor more LANs which overlap, with one or more nodes and/or access pointscommon to one or more LANs. Alternate embodiments may have additionalLANs, which may or may not overlap with each other. In the presentlypreferred embodiment, the network address of a node is obtainedaccording to the process described in connection with FIG. 3 below.

DNS server 203 maintains network addresses for the nodes of the LANnetwork that it is associated with. As discussed above, a DNS server maybe associated with one or more LANs and maintain the network addressesof nodes within one or more LANs. In one preferred embodiment, a noderegistered with several access points may have at least as many networkaddresses. The network addresses for the nodes may be included in theDNS server, or node route registry. Additionally, the DNS server mayalso maintain address allocation information such as node addressallocation indicator (or node preference indicator). Table 1 below showssome of the information which may be included in maintaining networkaddresses for nodes in a LAN. The resource records maintained in the DNSserver may include:

TABLE 1 Resource Node Network Node Address Preference Record TypeAddress Node Name Indicator AAAA ADDR1 MAC1 50 ADDR2 30 ADDR2 10 AAAAADDR4 MAC2 80 AAAA ADDR5 MAC3 44 ADDR6 20

As illustrated in Table 1, in the presently preferred embodiment thenode name is the MAC address of the node. However, other embodiments mayuse other names for the node, which may or may not include or be basedupon the MAC address. Further, the Resource Record (RR) Type in table 1may be an IPv6 type.

Information in the route registry may be updated according to multiplecriteria, including periodically or in the event one or more criteriaare satisfied.

For illustration purposes only one DNS server is shown and discussedbelow. Alternate embodiments, however, may use multiple DNS servers.

Alternate embodiments of the DNS resource records may include additionalinformation or may exclude some of the information included in Table 1.Additionally, while Table 1 includes information on only three nodes,alternate embodiments of a route registry could have information on moreor fewer nodes. While Table 1 includes up to three network addresses fora given node, alternate embodiments of a route registry may have anynumber of addresses per node.

FIG. 3 is a generalized flow diagram of a process 300 for obtaining anetwork address of a node. At step 301 a node intending to send a packetor a message to a node makes a DNS resolution request to a DNS server.The DNS resolution request includes a node identifier, typically thenode name. The node identifier may be any combination of letters,numbers, symbols or characters. As described above in connection withTable 1, in one presently preferred embodiment the node identifier isthe MAC address of the intended node. As shown in Table 1, the source orrequesting node includes information specifying the node's identifier,the node's network address, network address preference, etc. At step 302the DNS server receives the DNS resolution request for the intendednode. At step 303 the DNS server responds with a network address for thenode associated with the node identifier. In the presently preferredembodiment, the network address is an IP address. In one presentlypreferred embodiment, the resource record AAAA relates to an IPv6address. IPv4 resource record (RR) may be A, PTR, CNAME type. The DNSserver may have more than one network address for a given node. Forexample, multiple IPv6 addresses may be associated with a given node (oraccess point, or BOS, or any other device on a network). If multipleaddresses are associated with a given node, at step 302 the DNS servermay provide all available network addresses for a particular RR.Alternatively, the DNS server may select a subset of the networkaddresses associated with the intended node. For example, the DNS servermay choose one network address to include in the response to theelectronic device. If a subset of network addresses associated with theintended node is selected the selection may be based upon a connectioncost, upon a preset selection criteria, upon a policy (for example, theelectronic device intending to exchange messages with the node, thetype, size or priority of the message, some aspect of the use of themessage by the node, or the nature of the network device e.g.: a server,a network management system, a billing system, an outage managementsystem, a utility management system, etc.) or upon some other criteria.If multiple network addresses are provided in the DNS resolutionresponse, the response may also include the corresponding node addresspreference indicators. At step 304 the node receives the DNS resolutionresponse from the DNS server. At step 305 the node sends its messageusing a network address received from the DNS server.

The address used to send the message from the node and/or an electronicdevice to the intended node or electronic device may correspond to oneor more access points. For example, in an IPv6 LAN the network addresswould typically be an IPv6 address. In the event there is more than oneaccess point, the IPv6 prefix of the network address may be associatedwith a given access point. In this manner the IPv6 network address mayallow a given access pint to be used to transmit a message to thenetwork destination. If a node is in a LAN with multiple access points,the node may have more than one IPv6 address associated with the node.

EXAMPLE 1 Multi Ingress Using IPv6 Network Addressing

The present example has a given node with a node name of Node1. Node1has two IPv6 network addresses associated with it. The route registryentry for Node1 may read:

DDNS Route Registry Node Address Node Resource Preference Name RecordType Node Network Address Indicator . . . . . . . . . . . . MAC1 AAAA2001:2105:20ae:1:225:3400:208:aa03 50 2001:2105:20ae:2:225:3400:208:aa0330 . . . . . . . . . . . .

-   -   Node1 connects to a communications network through two access        points: AP1 and AP2. AP1 is associated with IPv6 prefix        2001:2105:20ae:1::/64 and AP2 is associated with IPv6 prefix        2001:2105:20ae:2::/64.    -   A network device, for example a back office system which manages        outage detection, intending to send a message to Node1 may        receive either network address associated with Node1 from the        route registry of the DNS server (or may receive both network        addresses). A message sent from the outage detection system to        Node1 using the network address with prefix        2001:2105:20ae:2::/64 would be routed through AP2. A message        sent from the outage detection system to Node1 using the network        address with prefix 2001:2105:20ae:1::/64 would be routed        through AP1.

FIG. 4 is a generalized communications flow diagram illustrating process400 for registering a nodal device with an access point. Registering anodal device to obtain a network address may apply to any format orprotocol of network addresses. In one presently preferred embodiment,the LAN may be using IPv6 protocols (exclusively or in parallel withIPv4 protocols). For discussion purposes, process 400 will describenodes of a wireless LAN using IPv6 network addresses. In a presentlypreferred embodiment, Node M initiates a discovery process andidentifies its neighbor nodes and the access points of one or more LANswhich provide egress and ingress. Node M may further initiate a routinganalysis to identify a preferred set of one-hop neighbors who provideegress via one or more access points at the lowest path cost. It maythen commence registration process with one or more APs and theaffiliated DNS servers. At 401 node M sends a layer 2 registrationmessage to an access point AP. At 402 the AP responds with a layer 2acknowledgement message including an IPv6 prefix which is associatedwith the AP. Additionally, the acknowledgement message may includeconfiguration information. In a presently preferred embodiment, theconfiguration information includes information which allows node M toregister with a DNS server. In Another embodiment the AP may proxy theDNS request on behalf of node M. At 403 node M receives the layer 2acknowledgement message and sends a layer 3 IPv6 registration message tothe DNS. In one presently preferred embodiment, the IPv6 registrationmessage to the DNS includes the IPv6 address for node M, which utilizesthe IPv6 prefix received from the AP and a unique IPv6 “suffix”, tocomplete an IPv6 address for node M. This is done consistent withstateless autoconfiguration steps of RFC 2462. In one preferredembodiment, the IPv6 suffix is based upon the MAC address of the node M.Alternate embodiments may use other suffixes not based upon the MACaddress to create a unique IPv6 address for the node M. Note, the IPv6address for node M need not be globally unique.

At 404 a layer 3 acknowledgement message is sent from the DNS to thenode M and received by the node M at 405. The layer 3 acknowledgementmessage may include confirmation of the registration of node M'sregistration with the DNS server, and may include additionalinformation.

While process 400 only shows the registration of one node with oneaccess point, in the presently preferred embodiment all nodes wouldregister with at least one access point. Additionally, in one presentlypreferred embodiment nodes would register with more than one accesspoint on their LAN in the event there is more than one access point onthe LAN associated with the node. A node may even register with all theaccess points on the LAN the node is associated with.

In the presently preferred embodiment, a given node may have more thanone unique IPv6 address associated with the node. If, as describedabove, a node's IPv6 address is determined from the IPv6 prefix of anaccess point and a unique component (e.g., the MAC address of the node)then if the node registers with multiple access points the node will beassociated with multiple unique IPv6 addresses. In this manner nodes maybe multihomed.

Node M may send a layer 3 SNMP TRAP or INFORM message to a back officesystem BOS at 406. Alternatively, the DNS server may signal the BOS viaSNMP. Preferably, the SNMP TRAP or INFORM message will include at leastone IPv6 address of the node M (and may include multiple networkaddresses associated with node M). At 407 the BOS receives the SNMP TRAPor INFORM message and replies with a layer 3 message such as a GMI(Generic Management Interface) data query. GMI data query message mayrequest information on node M. For example, if node M is a meter in autility network, the GMI data query message may request information onthe configuration settings of the meter, status of the meter,information on the metered commodity, etc. At 408 node M receives thedata query message and sends a data response message. At 409 the BOSreceives the data response message from node M.

The BOS may request the network address of a given node at any time. Forexample, if the BOS has not received a message from node M when amessage was expected, the BOS may query node M. If the BOS does notalready have the network address of node M, or, as in one presentlypreferred embodiment, if the network is configured to request a networkaddress unless the BOS is responding to a message received, the BOS mayperform a lookup (i.e. a DNS resolution request) with the DNS server. At410 the BOS sends an IPv6 network address lookup message for node M tothe DNS server. At 411 the DNS server responds to the BOS with an IPv6address for node M to the BOS (if the DNS server has a network addressfor node M, otherwise the DNS server may respond that it does not have anetwork address for node M). The IPv6 address for node M is received at412.

In the event the node is not registered, or if the BOS does not receivea network address for the node, the BOS may attempt to programmaticallyderive the IP address or may attempt to generate an IP address. The BOSmay create an ad-hoc IPv6 address using the AP's IPv6 address and thenode's MAC address (as described above). The BOS may also send an IPv6message to the AP requesting the AP to forward a message to the nodebased upon the node according to the node's unique MAC identifier.Alternatively, the BOS may request the AP ping the node to determine thenetwork address of the node and/or inquire into the results of theregistration process.

In the event node M encounters a problem, for example loss of power, asecurity incident, a problem with its hardware or software, a networkproblem, etc., node M may send a message indicating a problem to the BOS(or to any device reachable by node M) such as an SNMP TRAP or INFORMmessage. In the event of a loss of power, the node M may send a “lastgasp” message. At 413 node M sends a last gasp message to the AP.Typically, the layer 2 last gasp message is very short with only theessential information to conserve node's and network's resources, so themessage is received reliably by other neighbor nodes and thecorresponding AP. At 414 the AP receives the last gasp message from nodeM, and in the presently preferred embodiment packs an SNMP TRAP orINFORM PDU (Protocol Data Unit or SNMP packet) with L2 “last gasp”messages and forwards them to the BOS which indicates the AP hasreceived a last gasp message from node M.

EXAMPLE 2 Network Addressing for Transportation Nodes

The present example has a given node that is a transportation device asshown in FIG. 5. Specifically, Node H is a hybrid car which may have itsbatteries charged from an electric grid. Upon plugging Node H into anelectrical outlet node H attempts to establish communication with anelectrical utility billing BOS called BOS-HB. In the present exampleNode H is within the coverage area of LAN-7, a wireless communicationsnetwork using the IPv6 protocol. Node H sends a layer 2 registrationrequest message to at least one access point within LAN-7. AP1, anaccess point with LAN-7 responds with its IPv6 prefix, which is 4ea3.Node H uses the received prefix from AP1 to create a unique IPv6address. Node H uses the MAC address of a network card in Node H, alongwith the IPv6 prefix from AP1, to create the unique IPv6 address. Node Hsends a layer 3 registration message to a DNS server associated withLAN-7 and receives an acknowledgement from the DNS server. Node H alsoregisters with a second access point on LAN-7 called AP2. AP1 and AP2are both capable of communicating with BOS-HB through a communicationsnetwork. AP2 sends Node-H its IPv6 prefix of 21 ff, which Node H uses tocreate a second unique IPv6 address associated with AP2. Node H thensends an SNMP TRAP or INFORM message to BOS-HB indicating that it is onLAN-7. Additionally, the message to BOS-HB includes information to alertBOS-HB that Node H is currently connected to the electrical grid andreceiving power to recharge the batteries of Node H. BOS-HB sends Node Hmessages to inquire into the electrical usage of Node H and also sendsmessages to check if Node H is still on the network. Prior to sending amessage to Node H, BOS-HB performs a lookup of Node-H's network addresswith the DNS server. The DNS server, in responding to lookup requestscorresponding to Node-H, may determine which of the two unique IPaddresses associated with Node H to provide BOS-HB. In this exampleembodiment, the route registry of the DNS server includes a uniquepreference indicator associated with the IPv6 addresses corresponding toNode H. The preference indicator specifies that AP2 is preferred overAP1, as AP2 has a more reliable connection with AP2 than with AP1. Thus,the DNS server replies to BOS-HB with the network address associatedwith AP2. BOS-HB then uses the network address associated with AP2,which then routes messages to Node-H through AP2. In the event of afailure to deliver a message from BOS-HB to Node-H through AP2, BOS-HB(or another device on the network) may request and receive the next mostpreferred network address associated with Node-H, and resend the failedmessage using the next most preferred network address for Node-H. As thenext most preferred network address for Node-H corresponds to AP1, theretry of the failed message is routed through AP1 to Node-H. In responseto the failed delivery message to the network address associated withAP2, the DNS server may change the preference indicators associated withone or more network addresses associated with Node-H, and may alsochange the preference indicators of other nodes on according to one ormore criteria (e.g. proximity to Node-H, dependence on AP2, dependenceon Node-H, etc.). The request to change the preference indicator in theDDNS registry may originate from any one of Node-H, the BOS-HB, AP-1,AP-2.

Node H responds to the request from BOS-HB received from AP2 by sendinga packet including the network address of Node H. If the includednetwork address includes the prefix of AP1, the pack may be routedthrough AP1 to BOS-HB, thus allowing a network address to determinewhich access point, from among multiple access points, to use inegressing from LAN-7. Node H may select which of multiple networkaddresses associated with Node H to include in packet's header sent fromNode H. By routing packets based upon the access point prefix includedin the Node H, the egress point of the LAN may be selected, allowingcontrol of egress in multi-egress embodiments.

As Node H is a mobile node capable of moving from one location toanother (which may result in moving out of direct contact with a givenAP, node or LAN), the AP may deregister a mobile node. For example,mobile nodes may be deregistered if they have not been in communicationwith the AP for a preset or configurable, period of time. Additionally,or alternatively, mobile nodes may send information to one or more APsnot to deregister them, or policies at the AP may decide not toderegister a given mobile node based upon one or more characteristics.

System Components in Support of IPv6 Utility Networks

Utility networks capable of supporting communication using IPv6addressing and protocols may use a variety of devices capable ofcommunicating, preferably, using IPv6. In the presently preferredembodiment, system components such as a utility node, an access point,and a back office system would have IPv6 functional support integratedinto the respective system component. Example preferred embodiments ofIPv6 capable systems components are shown and described in connectionwith FIGS. 6, 7 and 8.

FIG. 6 is a generalized block diagram of a node 600 as may be found incommunications network 600 described above. In one preferred embodiment,node 600 may include a device information controller 601, memory 602,LAN radio controller and interface 603, private radio controller andinterface 604, meter and external data interface 605, and IPv6 protocolcontroller 609. Meter and external data interface 605 may connect to aslave device 606, local meter data interface 607, and or an externalsensor device output interface. IPv6 protocol controller 609 may receiveand send IPv6 packets, and may also create or maintain IPv6 tunnels orencapsulate/de-encapsulate packets as needed.

While the example node 600 does not include a meter for metering acommodity, alternate embodiments may include metering capability.

While the example node 600 does not include radios such as a privatenetwork radio or LAN radio, alternate embodiments of the node mayinclude one or more radios.

While example node 600 is described as a single device, alternateembodiments may use multiple computers, electronic devices or radios inimplementing example node 600.

FIG. 7 is a generalized block diagram of an access point 700 as may befound in communications network 600 described above. Access point 700,which may also act as a gateway to nodes in a network such as a wirelessLAN, may include an access point information controller 701, memory 702,a WAN interface 703, a private wireless radio network controller 704, awireless LAN radio controller and interface 705, and network IDs IPv6protocol controller 706. The network IDs IPv6 protocol controller 706may also include a tunnel broker, or a tunnel broker may be includedseparately from the router and 6-in-4 formatter in embodiments utilizinga tunnel broker.

While the example access point 700 does not include radios such as aprivate network radio, WAN or LAN radio, alternate embodiments of theaccess point may include one or more radios.

While the example access point 700 is distinct from a meter or otherdevice in the network (e.g. a relay, etc.) alternate embodiments couldcombine the functionality of a node, meter, relay, or any other deviceor system in the network.

While access point 700 is described as a single device, alternateembodiments may use multiple computers, electronic devices or radios inimplementing access point 700.

FIG. 8 is a generalized block diagram of back office system 800 as maybe found in communications network 500 described above. Back officesystem 800 may include a communications server 801, a wireless privatenetwork communications controller 802, a router and 6-in-4 formatter803, an application server 804 and a database server 805. Wirelessprivate network communications controller 802 may communicate with aprivate wireless network. The router and 6-in-4 formatter 803 maycommunicate with the WAN. The router and 6-in-4 formatter may alsoinclude a tunnel broker, or a tunnel broker may be included separatelyfrom the router and 6-in-4 formatter in embodiments utilizing a tunnelbroker. The WAN may be the internet, an intranet, or any other type ofwide area network. Application server may be any type of applicationwhich may be used in a utility network. Examples, without limitation,include billing applications, accounting applications, outage detectionand/or management applications, configuration and or provisioningapplications, network applications such as a proxy server, a DNS or DNSserver, a storage, back-up and or recovery application, a customerinterface application (for example, an interface application to allow acustomer to control aspects associated with a node or to control aspectsof a node), a node manager, a content management or delivery system, acommunication manager or communication providing application, etc.Alternatively, the formatter may be a 6 to 4 formatter for IPv6 packetencapsulation.

While back office system 800 is described as a single entity, it may beimplemented on one or more computers, for example on multiple servers ina data center. The described components of back office system 800 may beimplemented on different computers, or may be implemented acrossmultiple computers. Additionally, back office system 800 may beimplemented across multiple computers in multiple locations or onmultiple networks. Back office system 800 may also aggregate or includemultiple applications. For example, a back office system may includeboth an accounting system as well as a customer billing system. Asanother example, back office system may include a billing system and aproxy server. Additional combinations of any number of applications maybe included in additional alternate embodiments.

Utility Node Subnetworks

FIG. 9 is a generalized block diagram illustrating a utility nodesub-network 900. Network 900 may include a utility node 901. The utilitynode may include a commodity meter, or may interface with a commoditymeter. Utility node 901 is capable of communicating with acommunications network 902. In one preferred embodiment, utility node901 includes a wireless radio capable of communicating with a wirelessLAN using IP protocols (IPv4 or IPv6). Utility node 901 also includes anin-premise device interface 903. In-premise device interface 903connects to in-premise devices 904 to provide a communications linkbetween the utility node and the in-premise devices. Additionally, theutility node may provide a communications link between the in premisedevices 904 and the communications network 902 connected to the utilitynode.

In one presently preferred embodiment, the utility node in-premisedevice interface 903 assigns a network address to in premise deviceswhich it is capable of communicating with. In one possible embodiment,the network address assigned by the in-premise device interface 903 isan IP address. Preferably, the network address assigned to an in-premisedevice is unique within communications network 902. The in-premisedevice interface 903 may also share, or allow sharing, of the networkaddress assigned to an in-premise device outside of the subnet withinthe premise. Thus, in-premise devices are directly addressable fromoutside the sub-network of the premise. The utility node proxies theassigned IP address on behalf of the corresponding in-premise device,allowing other nodes in the communication network to communicate withthe in-premise device using the assigned IP address. Example 3illustrates this through one possible embodiment.

EXAMPLE 3 In-Premise Communication Using IPv6 Network Addressing

The present example is of a utility node with a node name of Node 31Cedar Ave. Node 31 Cedar Ave is deployed in a residential unit (a home)and is capable of communicating with in-premise devices (devices withinthe home) through multiple protocols and communications technologies.For example, utility node 31 Cedar Ave may communicate with devicesusing ether a wireless personal area network (WPAN) or using PLC (Powerline Carrier) communications with PLC capable devices connected to thehome's power grid.

The example home includes five in-premise devices, a thermostatcommunicating via WPAN, a pool pump communicating via WPAN, a freezercommunicating via PLC, and a home entertainment system communicating viaWPAN.

The WPAN may be any one, or any combination, of network technologies orstandards including, without limitation, Bluetooth, ZigBee (IEEE802.15.4), IrDA, UWB (IEEE 802.15.3), Dust TSMP, Insteon, othertechnologies based upon IEEE 802.15, etc.

Utility Node 31 Cedar Ave communicates wirelessly with a utility networkusing IPv6 communications protocols. The utility network includes otherutility nodes and at least one access point, as well as a BOS formanaging node 31 Cedar Ave.

Utility Node 31 Cedar Ave includes an electricity usage meter whichmonitors and reports the electrical usage of the home. Additionally,Node 31 Cedar Ave includes an interface for other commodity meters,which is connected to a natural gas meter which monitors and reports thenatural gas usage of the home.

Node 31 Cedar Ave assigns an IPv6 address to each of these in-premisedevices. Node 31 Cedar Ave shares the assigned IPv6 address for thethermostat, pool pump, freezer and entertainment system withcommunications network. Specifically, the network addresses of thein-premise devices are shared with an in-premise management portal whichis connected to the utility network and which allows the homeowner tomonitor and control the in-premise devices. The network addresses of oneor more in-premise devices may also be proxied by Node 31 Cedar Avewithin communications network or which may communicate through thecommunications network with Node 31 Cedar Ave.

Through the in-premise management portal the homeowner (or others) maycommunicate with the in-premise devices using the assigned IP address.Node 31 Cedar Ave receives packets intended for in-premise devices,identifies the intended device according to the assigned IP address, andforwards the payload of the packets to the intended device over theappropriate in-premise communication system (WPAN, PLC, etc.).Similarly, communication signals from the in-premise devise receivedover the in-premise communication system is input into the payload of apacket(s) and send to the in-premise management portal, including thenetwork address assigned to the in-premise device.

The in-premise registry entry for the in-premise devices may read:

In-Premise Registry Assigned In-Premise In-Premise IPv 6 NetworkCommunication Native Device Name Address Technology Address ThermostatAddress 1 ZigBee Z₁ Freezer Address 2 PLC PLC₁ Pool Pump Address 3ZigBee Z₂ Entertainment Address 4 ZigBee Z₃ System

Node 31 Cedar Ave uses the assigned network addresses and the in premisecommunication technology to allow communication between the in-premisedevices and outside of premise communications networks.

In one preferred embodiment the utility node may also maintain an accesscontrol list (ACL) for in-premise devices. Using the ACL, the utilitynode allows access to an in-premise device according to the ACL. Forexample, the ACL may specify that a home security system may only allowaccess from a security portal. Any device or system attempting tocommunicate with the home security system will be denied access unlessit provides the appropriate verification information specified in theACL as corresponding to the security portal.

The utility node ACL may also specify service ports or network daemonnames which are allowable for either, or both, inbound and outboundtraffic.

In one presently preferred embodiment, the utility node may assignroutable network addresses to in-premise devices. In premise devices maynot be capable of using the network address, as in Example 3 above,where WPAN and PLC devices use their own network address and haveassigned an IP address. Thus, the network address assigned thein-premise device is proxied by the utility node. In embodiments usingIPv6, an access point may assign a portion of its allocated IPv6addresses to the utility node. In turn, the utility node may allocateaddresses to in premise devices from the IPv6 addresses assigned theutility node. In one preferred embodiment, the AP may allocate a blockof continuous addresses to one or more utility nodes. The utility nodesmay then assign any of the allocated addresses, or portions of them, toin-premises devices.

The network address assigned a device may be, partially or entirely,based upon the MAC address of the utility node communicating with thedevice, an access point, or the device itself.

Additionally or alternatively, rules or policies may be used todetermine the allocation of addresses to in premise devices. Rules maybe based upon the device type, device attributes, network technology ornetwork protocol used by the device, the device's commodity usage type(e.g. electric, gas, water, etc.), the device's commodity usage historyor characteristic (e.g. high usage, moderate usage, etc.), the premiseor section of a premise the device is physically located in, or assignedattributes of the device (e.g. the importance of a device, the use of adevice such as medical equipment, fire suppression equipment, securityequipment, emergency response equipment, etc.), or upon attributesassigned by a user of the device or the owner/operator of the premise.Rules may also combine multiple factors listed above, for exampleconsidering the type of device, the physical premise, the electricalpower consumption, and whether the device is related to security oremergency response.

Additionally or alternatively, some network addresses may be set asidefor particular devices, uses, users, etc. For example, certain networkaddresses may be set aside for emergency personnel or their equipment.Thus, a mobile in-premise device of an emergency responder which appearson a given in-premise subnet may be assigned an address from a set-asidegroup of addresses for such devices of emergency responders. The addressgiven from the group of address set aside may also be allocatedaccording to a rule, for example assigning an address based upon thetype of responder (police, fire, EMT, etc.) their affiliation ororganization (department, precinct, etc.) the device type, or any otherattribute of the organization, purpose, device, etc.

Example 4 illustrates one possible embodiment for implementingallocation of addresses to utility nodes and the assignment of allocatedaddresses to in-premise devices using utility nodes.

EXAMPLE 4 Assigning In-Premise IPv6 Network Addresses

A utility node with a node name of Meter HM is deployed in a residentialunit (a home) and is capable of communicating with in-premise devices(devices within the home or neighboring homes) through multipleprotocols and communications technologies. Additionally, Meter HM alsoincludes a commodity meter which meters the electricity used in thehome. Meter HM may communicate with devices using either WPAN or PLC,with PLC capable devices connected to the home's power grid. The homeincludes six in-premise devices which may communicate with Meter HM: athermostat communicating via WPAN, a freezer communicating via PLC, ahome alarm system communicating over WPAN, a video camera which monitorsa portion of the home and communicates over WPAN, a health monitoringsystem which may monitor the health of an elderly relative and whichcommunicates over WPAN, and a home entertainment system communicatingvia WPAN.

Meter HM communicates wirelessly with a utility network using IPv6communications protocols. The utility network includes other utilitynodes and at Access points AP214, AP137 and AP8, as well as a BOS formanaging Meter HM. The BOS also includes a customer portal which allowsthe homeowner to either monitor or control, or both, some or all of thein premise devices.

Access points AP214, AP137 and AP8 each have a /64 allocation of IPv6addresses. Access point AP137 has allocated a /125 of IPv6 addresses toutility node Meter HM. Meter HM selects addresses from its /125allocation of IPv6 addresses to assign addresses to the in-premisedevise which register with it. Meter HM assigns addresses to thethermostat communicating via WPAN, the freezer communicating via PLC,the home alarm system communicating over WPAN, the video cameracommunicates over WPAN, the health monitoring system communicating overWPAN, and the home entertainment system communicating via WPAN. In theevent one or more in-premise devices is removed, or unregistered fromMeter HM then Meter HM may reassign the network address assigned to theremoved or unregistered in-premise device to another in premise device.

Allocation of blocks of addresses to utility nodes may be segregatedaccording to various criteria. For example, different sections of theutility network, geographically or logically, may have address blocksallocated from a subset of available address blocks.

While the above example embodiments had the in-premise devicescommunicate with a utility node which is assigned to (or installed at)the some premise of the utility node, alternate embodiments may allowin-premise devices to communicate via utility nodes from neighboringpremises.

While the above example used continuous blocks of a given size accordingto CIDR (Classless Inter-domain routing) notation, alternate embodimentscould use address blocks of any size, whether continuous ornon-continuous.

Transit of Packets from an IPv6 Node Through IPv4 Network

Determination of whether to use “6 to 4” or “6 in 4” communicationthrough an IPv4 network may be made by the access point, the back officesystem, or another component of the system. Communication between anIPv6 node in the utility network through an IPv4 network may be througheither “6 to 4” or “6 in 4” communication, according to the type ofnode, the type of network, the selected access point, the back officesystem, the type of message, the contents of the message, the desiredsecurity level, etc. For example, for increased security “6 in 4”communication may be used. Note, “6 in 4” communication is oftenreferred to as tunneling, whereas “6 to 4” communication is oftenreferred to as network address translations (NAT) or IPv6 packetencapsulation.

FIG. 10 is a generalized block diagram illustrating a network 1000 wherean IPv4 tunnel connects an IPv6 LAN to and IPv6 back office system.Network 1000 includes two local area networks 1001 and 1002. LANs 1001and 1002 include nodes 1003. In the presently preferred embodiment,nodes 1003 are utility nodes. LAN 1002 is connected to access point AP11004. LAN 1001 is connected to access points AP2 1005 and AP3 1006.Access point AP1 1004 and access point AP2 1005 connect tocommunications network 1007. Access point AP3 1006 connects tocommunications network 1008. In the presently preferred embodiment,communications networks 1007 and 1008 are wide area networks. Backoffice system BOS-1 1009 connects to WAN 1007. Back office system BOS-21010 connects to WAN 1007 and WAN 1008. Back office system BOS-3 1011connects to WAN 1008.

In the example embodiment, LANs 1001 and 1002 communicate using the IPv6protocol. Similarly, WAN 1008 utilize the IPv6 communications protocol.Access point AP3 1006, connecting LAN 1001 to WAN 1008, utilizes IPv6.Back office Systems BOS-1 1009, BOS-2 1010 and BOS-3 1101 all utilizethe IPv6 communications protocol.

WAN 1007 is an IPv4 network, and does not support IPv6. Access points1004 and 1005 which connect LAN 1002 and 1001, respectively, to WAN 1007are capable of communicating using IPv6 and in participating in amechanism that facilitates transit of IPv6 packets through WAN 1007 toBOS 1009 and 1010, and vice versa.

A message from a node 1003 on LAN 1002, intended for BOS-1 1009 or BOS-21010, is sent using and IPv6 address and packet format to access pointAP1 1004. AP1 1004 creates and uses an IPv6 tunnel (dynamically ormanually configured) through WAN 1007. An IPv6 packet from a node 1003on LAN 1001 to BOS-2 1010 may route the packet through WAN 1007 orthrough WAN 1008. If the IPv6 packet is to be routed through WAN 1008,AP3 1006 is used and as WAN 1008 is an IPv6 network, no tunneling,translation or encapsulation need be performed. However, if the packetis routed through WAN 1007, then AP2 1005 is used an the IPv6 packetfrom node 1003 will either be passed through a “6-in-4” tunnel, asdescribed in Figure, or may be encapsulated in an IPv4 packet fortransit through WAN 1007 in a 6to4 virtual tunnel, as described below inconnection with FIG. 12.

As shown in FIG. 11, packet flow between the access point associatedwith the IPv6 LAN and the BOS is through the IPv4 WAN.

FIG. 12 is a generalized block diagram illustrating a network 1200 whereIPv6 packets are passed through an IPv4 WAN. Network 1200 may includetwo local area networks 1201 and 1202. LANs 1201 and 1202 include nodes1203. In the presently preferred embodiment, nodes 1203 are utilitynodes. LANs 1201 and 1202 communicate with nodes 1203 using IPv6protocols and addressing. LAN 1202 is connected to access point AP11204. LAN 1201 is connected to access points AP2 1205 and AP3 1206.Access point AP1 1204 and access point AP2 1205 connect tocommunications network 1207. Access point AP3 1206 connects tocommunications network 1208. In the presently preferred embodiment,communications networks 1207 and 1208 are wide area networks whichcommunicate using IPv4 protocols and addresses. Back office system BOS-11209 connects to WAN 1207. Back office system BOS-2 1210 connects to WAN1208. Back office system BOS-3 1211 connects to WAN 1208.

A node 1203 on LAN 1201 or 1202 sending a message to one, or more, ofthe back office systems BOS-1, BOS-2, and BOS-3 must pass through one ormore IPv4 WANs 1207 or 1208.

Node 1203 on LAN 1201 or 1202 sends an IPv6 packet using and IPv6address to the appropriate access point to communicate with the intendedback office system. In the event BOS-1 1209 is the intended back officesystem, AP1 1204 may be used to connect to WAN 1207. AP1 1204 receivesthe IPv6 packet from node 1203, and may encapsulate the received IPv6packet in the payload portion of an IPv4 packet. AP1 may have or acquirea global IPv4 address for itself for this purpose. The IPv4 header withProtocol 41 is prepended to the IPv6 packet. An IPv4 address associatedwith BOS-1 is used in the IPv4 packet with the IPv6 packet as payload(the IPv6 packet is a datagram within the IPv4 packet). The IPv4 addressof BOS-1 for the prepended packet header can also be derived from theIPv6 destination address of the encapsulated packet by extracting the32-bits following the IPv6 destination address' 2002::prefix. In such anembodiment, the IPv4 source address in the prepended packet is the IPv4address of AP1. The packet IPv4 packet is then transmitted to BOS-1 1209through WAN 1207. BOS-1 1209 receives the IPv4 packet, and extracts theencapsulated IPv6 packet. The payload of the IPv6 packet is extracted bythe BOS-1 1209. In this manner AP1 1204 and BOS-1 1209 use a “6 to 4”tunnel translation though IPv4 WAN 1207 without establishing an explicittunnel.

Alternatively, AP1 1204 receiving the IPv6 packet from node 1203, andencapsulate IPv6 packets within UDP packets for transmission to BOS-11209 using WAN 1207. As above, in this manner AP1 1204 and BOS-1 1209are able to exchange IPv6 packets through IPv4 WAN 1207.

BOS-1 1209 intending to send a message to node 1203 through IPv4 WAN andIPv6 LAN may send an IPv4 packet to AP1 1204 through WAN 1207. AP1 1204may prepend an IPv6 prefix to the IPv4 address of the packet receivedfrom BOS-1 1209 and intended for node 1203, allowing the IPv4 address tobe effectively converted for transmitting the received packet over IPv6LAN 1201.

In yet another alternative embodiment, an IPv6 “explicit tunnel” may becreated through one or more IPv4 WANs (or more than one IPv6 tunnels maybe created through a given IPv4 WAN) as also discussed above inconnection with FIG. 10. For example, Node 1203 on LAN 1201 or 1202sends an IPv6 packet using and IPv6 address to the appropriate accesspoint to communicate with the intended back office system. In the eventBOS-1 1209 is the intended back office system, AP1 1204 may be used toconnect to WAN 1207. AP1 1204 receives the IPv6 packet from node 1203,and may establish an IPv6 tunnel (or may access an established IPv6tunnel) through IPv4 WAN 1207. A tunnel broker (not shown) may establishan IPv6 tunnel through IPv4 WAN 1207. This is a configured tunnel(referred to as 6in4 tunnel) where the traffic between nodes on eitherside intended BOS and AP nodes will, in the presently preferredembodiment, always use this tunnel. A configuration script may beexchanged between the access point of the utility network and a backoffice system in establishing the tunnel through the wide area network.In one preferred embodiments, AP1 1204 establishes the IPv6 tunnel toBOS-1 1209. However, alternate embodiments may have one or more backoffice systems establish a “6 in 4” tunnel through a WAN to one or moreaccess points. 6in4 tunnel is a configured tunnel. In alternateembodiments, UDP encapsulation of IPv6 packets may also be used, forexample to prevent the transiting packet through WAN 1207 is not blockedby any NAT (Network address Translation) device that may be present inWAN 1207.

The IPv6 packet IPv4 received by AP1 1204 is transmitted to BOS-1 1209via the “6 in 4” tunnel through WAN 1207. BOS-1 1209 receives andprocesses the IPv6 packet. Similarly, BOS-1 1209 may send IPv6 packetsto Node 1203 through AP1 1204 using the “6 in 4” tunnel through WAN1207.

Transit of IPv4 Packets Through an IPv6 Utility Lan Network

FIG. 13 is a generalized block diagram illustrating a network 1300 whereIPv4 packets are passed through an IPv6 LAN. Network 1300 may includetwo local area networks 1301 and 1302. LANs 1301 and 1302 include nodes1303. In the presently preferred embodiment, nodes 1303 are utilitynodes. LAN 1302 is connected to access point AP1 1304. LAN 1301 isconnected to access points AP2 1305 and AP3 1306. Access point 1304 andaccess point 1305 connect to communications network 1307. Access point1306 connects to communications network 1308. In the presently preferredembodiment, communications networks 1307 and 1308 are wide areanetworks. Back office system BOS-1 1309 connects to WAN 1307. Backoffice system BOS-2 1310 connects to WAN 1307 and WAN 1308. Back officesystem BOS-3 1311 connects to WAN 1308.

Nodes 1312 on LAN 1301 are IPv4 nodes which communicate using IPv4,whereas LAN 1301 utilizes IPv6. Node 1312 sending a message to BOS 1310,which connects to LAN 1301 through IPv6 WANs and access points, may beaccomplished by node 1312 sending an IPv4 packet on LAN 1301.

Node 1312 sends its IPv4 packet to AP2 for forwarding to BOS-1 1309. Inthis case, AP2 has the capability to read the destination header in theIPv4 packet but does not reformat the packet; the packet traverses toBOS-1 1309 or BOS-2 1310 over IPv4 WAN 1307; BOS-1 1309 and BOS-2 1310both have the capability to strip the IPv4 packet, read the sourceinformation and the payload; BOS-1 1309 and BOS-2 1310 also generateIPv4 packets intended for IPv4 node 1312 for traverse through WAN 1307,and forwarding to node 1312 by AP2 1305.

In one possible alternative embodiment, AP2 1305 has the capability tomap and convert the IPv4 address and headers to IPv6 and also read andmap the payload on to IPv6 packet. From then on, the IPv6 packettraverses thro WAN 1307 in a 6to4 or 6in4 tunnels like all other IPv6packets do; BOS 1309 and BOS 1310 receive and process the reformattedIPv6 packet, and also generate an IPv6 packet in any response to orcommunication with node 1312. The return IPv6 packet is converted backto IPv4 format by AP2 1305 before it is forwarded to node 1312.

In yet another possible embodiment, the IPv4 packet from node 1312heading to BOS 1310 or BOS 1311 via IPv6 WAN is converted to IPv6 formatby AP2 1305 or AP3 1306, and forwarded to BOS 1310 or BOS 1311 (in thismanner, 6in4 or 6to4 tunneling need not be involved).

The invention has been described with reference to particularembodiments. However, it will be readily apparent to those skilled inthe art that it is possible to embody the invention in specific formsother than those of the preferred embodiments described above. This maybe done without departing from the spirit of the invention.

Thus, the preferred embodiment is merely illustrative and should not beconsidered restrictive in any way. The scope of the invention is givenby the appended claims, rather than the preceding description, and allvariations and equivalents which fall

-   -   within the range of the claims are intended to be embraced        therein.

1. A wireless communication system comprising: a plurality of utilitynodes capable of receiving commodity meter information, the utilitynodes connected in a utility network, the utility nodes including anin-premise interface; at least one access point connected in the utilitynetwork, the access point providing a block of network addresses to atleast one utility node in the utility network; wherein the in premiseinterface allocates a network address to an in-premise devicecommunicating over an in-premise network from the block of networkaddresses received from the access point.
 2. The wireless network systemof claim 1, wherein network addresses are IPv6 addresses.
 3. Thewireless network system of claim 1, wherein the network addresses areIPv4 addresses.
 4. The wireless network system of claims 2 and 3,wherein the block of network addresses received form the access point isa continuous block of network addresses.
 5. The wireless network systemof claims 2 and 3, wherein the allocation of the network address to thein premise device is in response to detection of the in-premise device.6. The wireless network system of claim 5, wherein the network addressallocated to the in-premise device is shared with at least oneadditional node in the utility network.
 7. The wireless network systemof claim 6, wherein the at least one additional node in the utilitynetwork is an access point.
 8. The wireless network system of claim 7,wherein the network address allocated to the in-premise device is sharedwith at least one additional node in the utility network in response tothe allocating utility node receiving an indication to share the networkaddress allocated to the in-premise device.
 9. The wireless networksystem of claim 1, 2 or 3, wherein the in-premise network is WPANnetwork.
 10. The wireless network system of claim 9, wherein the WPANnetwork uses a communication protocol chosen from: UWB communicationsprotocol, ZigBee communications protocol, UDP protocol, WAP protocol,OBEX protocol, L2CAP protocol, or Blue-tooth family of protocols. 11.The wireless network system of claim 1, wherein the in-premise networkalso includes a PLC communications network.
 12. The wireless networksystem of claim 10, wherein the utility node proxies the allocatednetwork address to the utility network.
 13. The wireless network ofclaim 12, wherein at least one back office system in communication withthe utility network receives the allocated network address proxied bythe utility node and sends at least one message to the in-premise deviceusing the allocated network address.
 14. The wireless network system ofclaim 1, wherein the utility node allocates a unique network addressesto each of a plurality of in-premise devices.
 15. The wireless networksystem of claim 1, wherein at least one of the plurality of in-premisedevices is physically located at a neighboring premise.
 16. A method ofcommunicating on a wireless utility network, comprising: receiving anindication of the existence of at least one in-premise device over anon-IP based communications network; receiving a block of networkaddresses from an access point in the utility network; allocating anetwork address to the in-premise device from the received block ofnetwork addresses; and sending an indication of the allocation of thenetwork address with the in-premise device to at least one other node inthe utility network.
 17. The method of claim 16, wherein the at leastone other node in the utility network is an access point.
 18. The methodof claim 16, wherein the associated network address is an IPv6 address.19. The method of claim 16, wherein the non-IP based communicationsnetwork is a WPAN network.
 20. The method of claim 19, wherein the WPANnetwork uses a communication protocol chosen from: UWB communicationsprotocol, ZigBee communications protocol, UDP protocol, WAP protocol,OBEX protocol, L2CAP protocol, or Blue-tooth family of protocols
 21. Themethod of claim 16, further comprising: receiving an indication of theexistence of a second in-premise device over a non-IP basedcommunications network; allocating a second network address with thesecond in-premise device; and sending an indication of the allocation ofthe second network address with the second in-premise device to at leastone other node in the utility network.
 22. The method of claim 21,further comprising: receiving a message from at least one of thein-premise devices intended for a node on the utility network, whereinthe received message was received from non-IP based communicationsnetwork; sending at least one packet on the utility network addressed tothe intended node on the utility network, wherein the at least onepacket sent includes the associated network address of the at least oneof the in-premise device associated with the received message.
 23. Themethod of claim 22, wherein the intended node on the utility network isan access point, the access point forwarding the packet to node on acommunication network the access point is in communication with.
 24. Themethod of claim 16, wherein the associated network address is an IPv4address.